docs: remove TT SKY26b delivery date and mainnet schedule - #2
Open
dmitrii-f-t27 wants to merge 1 commit into
Open
docs: remove TT SKY26b delivery date and mainnet schedule#2dmitrii-f-t27 wants to merge 1 commit into
dmitrii-f-t27 wants to merge 1 commit into
Conversation
The TT SKY26b shuttle order was cancelled and refunded in July 2026; no Trinity die exists and none is scheduled. This repo has not been updated since 2026-05-18, so it still states a chip delivery date and a mainnet date derived from it. In a token/mining protocol repo those read as schedule commitments. deployments/base-sepolia.md:50 — "Mainnet deployment on Base L2 scheduled for Q2 2027 (post TT SKY26b silicon delivery, December 2026)" replaced with: mainnet is not scheduled, it is gated on a silicon route, the TT SKY26b order was cancelled and refunded, no route is selected. README.md:8 — "Mining requires a physical TT SKY26b Trinity chip" restated as a design requirement, with the plain statement that no such chip exists and no fabrication route is currently selected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dmitrii-f-t27
force-pushed
the
fix/silicon-status
branch
from
August 11, 2026 11:50
aa5b697 to
9d7af55
Compare
Author
|
@gHashTag — this is one of six PRs from a documentation and CI audit across the Trinity repos. Requesting your review here; I do not have permission to add you as a reviewer on this repo, hence the mention. This one is the most time-sensitive of the set: the repo has not been touched since 2026-05-18, so it never saw the TT SKY26b cancellation. It still states a December 2026 delivery date and gates mining on a chip that was never fabricated. In a token protocol a stated date reads as a schedule commitment. The full set:
Each PR body states what it does not fix as well as what it does. They are independent — merge or reject them separately. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This repo's last commit predates the TT SKY26b cancellation, so nothing swept it. Two public surfaces still state a hard delivery date and a hard hardware dependency for a chip that was never fabricated.
In a token and mining protocol a stated date reads as a schedule commitment, which makes this the highest-consequence stale claim of the set.
deployments/base-sepolia.md:51— Mainnet deployment on Base L2 scheduled for Q2 2027 (post TT SKY26b silicon delivery, December 2026) → mainnet is not scheduled; it is gated on a silicon route; the order was cancelled and refunded; no route is currently selected.README.md:8— Mining requires a physical TT SKY26b Trinity chip → restated as a design requirement, with the plain statement that no such chip exists.The No chip, no TRI. Period. line is kept — with the correction above it now reads as the constraint it is.
Source for the cancellation:
trinity-papers-ruPR #18, merged 2026-07-31 — Кристаллы не изготавливались, маршрут отменён, средства возвращены. Corroborated bytri-net/README.md:29(Trinity silicon — NO ROUTE — no die exists, none is scheduled) andtrinity-s3ai/README.md:39.